Switch CI to self-hosted runners and parallelize tests to fix TF CPU timeouts - #2856
Merged
Merged
Conversation
divyashreepathihalli
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the change
The Test the code (tensorflow, keras-stable) job has been consistently timing out on GitHub Actions, running 6+ hours without completing on every PR and master, while JAX and Torch finish in 80-90 minutes.
Root Cause
TF eager mode on CPU is significantly slower for the repeated model instantiation pattern in KerasHub tests
Test suite has grown ~80 model families, all running sequentially on a 2-core ubuntu-latest runner
No timeout-minutes was set, so jobs run the full 6-hour GitHub default before being killed
Checklist